Adaptive radio access network bit rate scheduling

ABSTRACT

The described technology is generally directed towards adaptive radio access network bit rate scheduling. Minimum bit rates for user equipment can be adjusted in a manner that accounts for the impact of the minimum bit rates on network performance. Ranges of minimum bit rates can be established for user equipment, and minimum bit rates can be adjusted within the ranges. A minimum bit rate can be decreased when it produces a relatively higher impact on network performance, and the minimum bit rate can be increased when it produces a relatively lower impact on network performance.

BACKGROUND

Fourth generation (4G), fifth generation (5G) and subsequent generationcellular networks can assign minimum bit rates to user equipment.Minimum bit rates can be used to ensure quality of service (QoS). Forexample, minimum bit rates can be used to ensure the ability to streamvideo data at a certain quality and without interruptions.

Existing approaches to assigning minimum bit rates use constant targetbit rates, which can negatively impact network performance in somesituations. For example, although a constant high target bit rate canensure QoS satisfaction, it can also pose challenges when user devicesconfigured with the constant high target bit rate are located in badradio frequency (RF) conditions. In such a scenario, a radio accessnetwork (RAN) node, such as a base station, may allocate a large amountof radio transmission resources to meet the constant high target bitrate. As a result, the network can suffer from low spectrum efficiencyand increased inter-cell interference.

Low spectrum efficiency can result, e.g., from fewer resources beingallocated to other user equipment, including other user equipmentexperiencing good RF conditions for which it is relatively inexpensive,in terms of radio transmission budget, to provide a satisfactory QoS.Meanwhile, increased inter-cell interference can result from, e.g.,increased radio transmission time and/or increased power levelsassociated with transmissions to meet the constant high target bit rate.

The above-mentioned problems can be avoided to some extent by usinglower constant target bit rates. However, constant low target bit ratescan negatively impact overall QoS levels that might otherwise beachieved by user equipment over time. When a user equipment is in goodRF conditions, a higher minimum bit rate can improve QoS with arelatively small impact on the network and other user equipment.

The above-described background is merely intended to provide acontextual overview of some current issues and is not intended to beexhaustive. Other contextual information may become further apparentupon review of the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the subject disclosureare described with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 illustrates an example wireless communication system configuredto adjust minimum bit rates of user equipment, in accordance withvarious aspects and embodiments of the subject disclosure.

FIG. 2 illustrates an example general architecture of a systemconfigured to adjust minimum bit rates within a wireless communicationsystem, in accordance with various aspects and embodiments of thesubject disclosure.

FIG. 3 illustrates an example controller that can implement thecontroller illustrated in FIG. 2 , in accordance with various aspectsand embodiments of the subject disclosure.

FIG. 4 illustrates example generation and use of a minimum bit ratepolicy to adjust minimum bit rates, in accordance with various aspectsand embodiments of the subject disclosure.

FIG. 5 illustrates an example architecture of a system configured togenerate and deploy a policy to adjust minimum bit rates based onnetwork conditions, in accordance with various aspects and embodimentsof the subject disclosure.

FIG. 6 illustrates an example process to adjust minimum bit rates usinga system such as illustrated in FIG. 5 , in accordance with variousaspects and embodiments of the subject disclosure.

FIG. 7 is a table representing a portion of an example minimum bit ratepolicy, in accordance with various aspects and embodiments of thesubject disclosure.

FIG. 8 is a table representing example evaluation and update of aminimum bit rate policy, in accordance with various aspects andembodiments of the subject disclosure.

FIG. 9 is a flow diagram representing a set of example operations offirst network equipment in connection with adjusting minimum bit ratesbased on a minimum bit rate policy, in accordance with various aspectsand embodiments of the subject disclosure.

FIG. 10 is a flow diagram representing a set of example operations ofsecond network equipment in connection with adjusting minimum bit ratesbased on a minimum bit rate policy, in accordance with various aspectsand embodiments of the subject disclosure.

FIG. 11 is a flow diagram representing a set of example operations ofthird network equipment in connection with adjusting minimum bit ratesbased on a minimum bit rate policy, in accordance with various aspectsand embodiments of the subject disclosure.

FIG. 12 is a block diagram of an example computer that can be operableto execute processes and methods in accordance with various aspects andembodiments of the subject disclosure.

DETAILED DESCRIPTION

One or more embodiments are now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments. It is evident,however, that the various embodiments can be practiced without thesespecific details, and without applying to any particular networkedenvironment or standard.

One or more aspects of the technology described herein are generallydirected towards adaptive radio access network bit rate scheduling.Minimum bit rates for user equipment can be adjusted in a manner thataccounts for the impact of the minimum bit rates on network performance.Ranges of minimum bit rates can be established for user equipment, andminimum bit rates can be adjusted within the ranges. A minimum bit ratecan be decreased when it produces a relatively higher impact on networkperformance, and the minimum bit rate can be increased when it producesa relatively lower impact on network performance. Further aspects andembodiments of this disclosure are described in detail below.

As used in this disclosure, in some embodiments, the terms “component,”“system” and the like are intended to refer to, or comprise, acomputer-related entity or an entity related to an operational apparatuswith one or more specific functionalities, wherein the entity can beeither hardware, a combination of hardware and software, software, orsoftware in execution. As an example, a component can be, but is notlimited to being, a process running on a processor, a processor, anobject, an executable, a thread of execution, computer-executableinstructions, a program, and/or a computer. By way of illustration andnot limitation, both an application running on a server and the servercan be a component.

One or more components can reside within a process and/or thread ofexecution and a component can be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components can communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software application orfirmware application executed by a processor, wherein the processor canbe internal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can comprise a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components. While various components have been illustrated asseparate components, it will be appreciated that multiple components canbe implemented as a single component, or a single component can beimplemented as multiple components, without departing from exampleembodiments.

The term “facilitate” as used herein is in the context of a system,device or component “facilitating” one or more actions or operations, inrespect of the nature of complex computing environments in whichmultiple components and/or multiple devices can be involved in somecomputing operations. Non-limiting examples of actions that may or maynot involve multiple components and/or multiple devices comprisetransmitting or receiving data, establishing a connection betweendevices, determining intermediate results toward obtaining a result,etc. In this regard, a computing device or component can facilitate anoperation by playing any part in accomplishing the operation. Whenoperations of a component are described herein, it is thus to beunderstood that where the operations are described as facilitated by thecomponent, the operations can be optionally completed with thecooperation of one or more other computing devices or components, suchas, but not limited to, sensors, antennae, audio and/or visual outputdevices, other devices, etc.

Further, the various embodiments can be implemented as a method,apparatus or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable (or machine-readable) device or computer-readable (ormachine-readable) storage/communications media. For example, computerreadable storage media can comprise, but are not limited to, magneticstorage devices (e.g., hard disk, floppy disk, magnetic strips), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD)), smartcards, and flash memory devices (e.g., card, stick, key drive). Ofcourse, those skilled in the art will recognize many modifications canbe made to this configuration without departing from the scope or spiritof the various embodiments.

Moreover, terms such as “mobile device equipment,” “mobile station,”“mobile,” “subscriber station,” “access terminal,” “terminal,”“handset,” “communication device,” “mobile device” (and/or termsrepresenting similar terminology) can refer to a wireless deviceutilized by a subscriber or mobile device of a wireless communicationservice to receive or convey data, control, voice, video, sound, gamingor substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably herein and with reference to therelated drawings. Likewise, the terms “access point (AP),” “Base Station(BS),” “BS transceiver,” “BS device,” “cell site,” “cell site device,”“gNode B (gNB),” “evolved Node B (eNode B, eNB),” “home Node B (HNB)”and the like, refer to wireless network components or appliances thattransmit and/or receive data, control, voice, video, sound, gaming orsubstantially any data-stream or signaling-stream from one or moresubscriber stations. Data and signaling streams can be packetized orframe-based flows.

Furthermore, the terms “device,” “communication device,” “mobiledevice,” “subscriber,” “customer entity,” “consumer,” “customer entity,”“entity” and the like are employed interchangeably throughout, unlesscontext warrants particular distinctions among the terms. It should beappreciated that such terms can refer to human entities or automatedcomponents supported through artificial intelligence (e.g., a capacityto make inference based on complex mathematical formalisms), which canprovide simulated vision, sound recognition and so forth.

It should be noted that although various aspects and embodiments aredescribed herein in the context of 4G, 5G, or other next generationnetworks, the disclosed aspects are not limited to a 4G or 5Gimplementation, and/or other network next generation implementations,such as sixth generation (6G), as the techniques can also be applied,for example, in third generation (3G), or other wireless systems. Inthis regard, aspects or features of the disclosed embodiments can beexploited in substantially any wireless communication technology. Suchwireless communication technologies can include universal mobiletelecommunications system (UMTS), global system for mobile communication(GSM), code division multiple access (CDMA), wideband CDMA (WCMDA),CDMA2000, time division multiple access (TDMA), frequency divisionmultiple access (FDMA), multi-carrier CDMA (MC-CDMA), single-carrierCDMA (SC-CDMA), single-carrier FDMA (SC-FDMA), orthogonal frequencydivision multiplexing (OFDM), discrete Fourier transform spread OFDM(DFT-spread OFDM) , filter bank based multi-carrier (FBMC), zero tailDFT-spread-OFDM (ZT DFT-s-OFDM), generalized frequency divisionmultiplexing (GFDM), fixed mobile convergence (FMC), universal fixedmobile convergence (UFMC), unique word OFDM (UW-OFDM), unique wordDFT-spread OFDM (UW DFT-Spread-OFDM), cyclic prefix OFDM (CP-OFDM),resource-block-filtered OFDM, wireless fidelity (Wi-Fi), worldwideinteroperability for microwave access (WiMAX), wireless local areanetwork (WLAN), general packet radio service (GPRS), enhanced GPRS,third generation partnership project (3GPP), long term evolution (LTE),LTE frequency division duplex (FDD), time division duplex (TDD), 5G,third generation partnership project 2 (3GPP2), ultra-mobile broadband(UMB), high speed packet access (HSPA), evolved high speed packet access(HSPA+), high-speed downlink packet access (HSDPA), high-speed uplinkpacket access (HSUPA), Zigbee, or another institute of electrical andelectronics engineers (IEEE) 802.12 technology. In this regard, all orsubstantially all aspects disclosed herein can be exploited in legacytelecommunication technologies.

FIG. 1 illustrates an example wireless communication system configuredto adjust minimum bit rates of user equipment, in accordance withvarious aspects and embodiments of the subject disclosure. The examplewireless communication system 100 includes network nodes 131, 141 of aradio access network (RAN). The network nodes 131, 141 provide wirelesscommunication service in service areas 130, 140. User equipment (UE) inthe service area 130, such as UE 132, UE 133, and UE 134, can send andreceive communications via network node 131. UE 142 in the service area140 can send and receive communications via network node 141.

The network nodes 131, 141 can communicate with communication serviceprovider network(s) 110 via backhaul links 120, 125. The communicationservice provider network(s) 110 can include a variety of networkequipment, including, e.g., a non-real time RAN intelligent controller(RIC) 111 and a near-real time RIC 112. In some embodiments, thenon-real time RIC 111 can generate a policy 115 and provide the policy115 to the near-real time RIC 112, and the near-real time RIC 112 canapply the policy 115 via the network nodes 131, 141.

In some embodiments, the communication service provider network(s) 110can receive performance data 121, 126 from the network nodes 131, 141,and the communication service provider network(s) 110, e.g., thenon-real time RIC 111, can use the performance data 121, 126 to generatethe policy 115. The near-real time RIC 112 can use the performance data121, 126 and the policy 115 to determine minimum bit rate adjustments122, 127. The near-real time RIC 112 can send the minimum bit rateadjustments 122, 127 to the network nodes 131, 141, and the networknodes 131, 141 can apply the minimum bit rate adjustments 122, 127 inconnection with the service being provided to UEs 132, 133, 134 and UE142.

In general, in embodiments according to FIG. 1 , the wirelesscommunication system 100 can be configured to adjust minimum bit ratesused in connection with providing wireless communication service to UEs132, 133, 134, 142. The UEs 132, 133, 134, 142 can be associated withacceptable minimum bit rate ranges, and the wireless communicationsystem 100 can be configured to adjust minimum bit rates associated withUEs 132, 133, 134, 142 while remaining within their acceptable ranges.Minimum bit rates can be adjusted for uplink (UL) communications,downlink (DL) communications, or both. The wireless communication system100 can be configured to identify opportunities to improve networkperformance using minimum bit rate adjustments, and the wirelesscommunication system 100 can determine and deploy the minimum bit rateadjustments 122, 127 in order to improve network performance, while alsooptionally making adjustments to retain high quality of experience (QoE)for the UEs 132, 133, 134, 142.

Several different scenarios can give rise to degraded networkperformance which can be addressed by minimum bit rate adjustmentsaccording to this disclosure. A first example scenario involves networknode 131 and UEs 132, 133, 134. In the first example scenario, the UE134 is assigned a high minimum bit rate and is also in poor RFconditions, optionally with low modulation and coding scheme (MCS)throughput. As a result, the UE 134 can use a high number of the networknode’s 131 available physical resource blocks (PRBs). As another result,the network node 131 has limited remaining PRBs available for UEs 132,133, even though the UEs 132, 133 may be in better RF conditions than UE134. The network node 131 therefore can have lower overall cellthroughput and lower spectral efficiency, resulting in degradedperformance. Some embodiments of this disclosure can be directed toidentifying this first example scenario and addressing it by loweringthe minimum bit rate of UEs such as UE 134. Conversely, embodiments canidentify when network conditions have changed such thatrestoring/increasing the minimum bit rate of UE 134 can be accomplishedwithout degrading network performance.

A second example scenario involves network nodes 131 and 141, and UEs134 and 142. In the second example scenario, similar to the firstscenario, the UE 134 is assigned a high minimum bit rate and is also inpoor RF conditions, optionally with low modulation and coding scheme(MCS) throughput. As a result, the network node 131 may spend arelatively large amount of “airtime,” on UE 134, i.e., time during whichradio transmissions are being sent or received from UE 134. As anotherresult, the UE 142 and network node 141 can experience increasedinterference, and resulting degraded performance, in connection withwireless service provided to UE 142. Some embodiments of this disclosurecan be directed to identifying this second example scenario andaddressing it by lowering the minimum bit rate of UEs such as UE 134. Asin the first scenario, embodiments can identify when network conditionshave changed such that restoring/increasing the minimum bit rate of UE134 can be accomplished without degrading network performance.

Some embodiments can apply machine learning (ML) to continuouslyevaluate and improve minimum bit rates applied to UEs 132, 133, 134, 142under various different network conditions. For example, embodiments canuse the non-real time RIC 111 to evaluate performance data 121, 126 andto generate the policy 115, wherein the policy 115 includes minimum bitrates to apply to UEs 132, 133, 134, 142 under various different networkconditions. The policy 115 can be carried out by the near-real time RIC112, e.g., by using the policy 115 to identify the minimum bit rateadjustments 122, 127. The effectiveness of the policy 115 can besubsequently evaluated at the non-real time RIC 111, using subsequentperformance data 121, 126. The non-real time RIC 111 can modify thepolicy 115 and provide the modified policy 115 to the near-real time RIC112. A repeating cycle of receiving performance data 121, 126, modifyingthe policy 115, and employing the modified policy 115 to adjust minimumbit rates can be used to continuously improve the minimum bit rateadjustments 122, 127 that are employed under different networkconditions.

The non-limiting term “user equipment” can refer to any type of devicethat can communicate with network nodes 131, 141 in a cellular or mobilecommunication system 100. UEs 132, 133, 134, 142 can have one or moreantenna panels having vertical and horizontal elements. Examples of UEs132, 133, 134, 142 comprise target devices, device to device (D2D) UEs,machine type UEs or UEs capable of machine to machine (M2M)communications, personal digital assistants (PDAs), tablets, mobileterminals, smart phones, laptop mounted equipment (LME), universalserial bus (USB) dongles enabled for mobile communications, computershaving mobile capabilities, mobile devices such as cellular phones,laptops having laptop embedded equipment (LEE, such as a mobilebroadband adapter), tablet computers having mobile broadband adapters,wearable devices, virtual reality (VR) devices, heads-up display (HUD)devices, smart cars, machine-type communication (MTC) devices, augmentedreality head mounted displays, and the like. UEs 132, 133, 134, 142 canalso comprise IOT devices that communicate wirelessly.

In various embodiments, system 100 comprises communication serviceprovider network(s) 110 serviced by one or more wireless communicationnetwork providers. Communication service provider network(s) 110 cancomprise a “core network”. In example embodiments, UEs 132, 133, 134,142 can be communicatively coupled to the communication service providernetwork(s) 110 via network nodes 131, 141. The network nodes 131, 141(e.g., network node devices) can communicate with UEs 122, 123, and 124,thus providing connectivity between the UEs 132, 133, 134, 142 and thewider cellular network. The UEs 132, 133, 134, 142 can send transmissiontype recommendation data to the network nodes 131, 141. The transmissiontype recommendation data can comprise a recommendation to transmit datavia a closed loop multiple input multiple output (MIMO) mode and/or arank-1 precoder mode.

Network nodes 131, 141 can each have a cabinet and other protectedenclosures, computing devices, an antenna mast, and multiple antennasfor performing various transmission operations (e.g., MIMO operations)and for directing/steering signal beams. Network nodes 131, 141 can eachcomprise one or more base station devices which implement features ofthe network node. Network nodes can serve several cells, depending onthe configuration and type of antenna. In example embodiments, UEs 132,133, 134, 142 can send and/or receive communication data via wirelesslinks to the network nodes 131, 141. The dashed arrow lines from thenetwork nodes 131, 141 to the UEs 132, 133, 134, 142 represent downlink(DL) communications to the UEs 132, 133, 134, 142. The solid arrow linesfrom the UEs 132, 133, 134, 142 to the network nodes 131, 141 representuplink (UL) communications.

Communication service provider networks 110 can facilitate providingwireless communication services to UEs 132, 133, 134, 142 via thenetwork nodes 131, 141 and/or various additional network devices (notshown) included in the one or more communication service providernetworks 110. The one or more communication service provider networks110 can comprise various types of disparate networks, including but notlimited to: cellular networks, femto networks, picocell networks,microcell networks, internet protocol (IP) networks Wi-Fi servicenetworks, broadband service network, enterprise networks, cloud-basednetworks, millimeter wave networks and the like. For example, in atleast one implementation, system 100 can be or comprise a large-scalewireless communication network that spans various geographic areas.According to this implementation, the one or more communication serviceprovider networks 110 can be or comprise the wireless communicationnetwork and/or various additional devices and components of the wirelesscommunication network (e.g., additional network devices and cell,additional UEs, network server devices, etc.).

The network nodes 131, 141 can be connected to the one or morecommunication service provider networks 110 via one or more backhaullinks 120, 125. For example, the one or more backhaul links 120, 125 cancomprise wired link components, such as a T1/E1 phone line, a digitalsubscriber line (DSL) (e.g., either synchronous or asynchronous), anasymmetric DSL (ADSL), an optical fiber backbone, a coaxial cable, andthe like. The one or more backhaul links 120, 125 can also comprisewireless link components, such as but not limited to, line-of-sight(LOS) or non-LOS links which can comprise terrestrial air-interfaces ordeep space links (e.g., satellite communication links for navigation).Backhaul links 120, 125 can be implemented via a “transport network” insome embodiments. In another embodiment, network nodes 131, 141 can bepart of an integrated access and backhaul network. This may allow easierdeployment of a dense network of self-backhauled 5G cells in a moreintegrated manner by building upon many of the control and datachannels/procedures defined for providing access to UEs.

Wireless communication system 100 can employ various cellular systems,technologies, and modulation modes to facilitate wireless radiocommunications between devices (e.g., the UEs 132, 133, 134, 142 and thenetwork nodes 131, 141). While example embodiments might be describedfor 5G new radio (NR) systems, the embodiments can be applicable to anyradio access technology (RAT) or multi-RAT system where the UE operatesusing multiple carriers, e.g., LTE FDD/TDD, GSM/GERAN, CDMA2000 etc.

For example, system 100 can operate in accordance with any 5G, nextgeneration communication technology, or existing communicationtechnologies, various examples of which are listed supra. In thisregard, various features and functionalities of system 100 areapplicable where the devices (e.g., the UEs 132, 133, 134, 142 and thenetwork nodes 131, 141) of system 100 are configured to communicatewireless signals using one or more multi carrier modulation schemes,wherein data symbols can be transmitted simultaneously over multiplefrequency subcarriers (e.g., OFDM, CP-OFDM, DFT-spread OFMD, UFMC, FMBC,etc.). The embodiments are applicable to single carrier as well as tomulticarrier (MC) or carrier aggregation (CA) operation of the UE. Theterm carrier aggregation (CA) is also called (e.g., interchangeablycalled) “multi-carrier system”, “multi-cell operation”, “multi-carrieroperation”, “multi-carrier” transmission and/or reception. Note thatsome embodiments are also applicable for Multi RAB (radio bearers) onsome carriers (that is data plus speech is simultaneously scheduled).

In various embodiments, system 100 can be configured to provide andemploy 5G or subsequent generation wireless networking features andfunctionalities. 5G wireless communication networks are expected tofulfill the demand of exponentially increasing data traffic and to allowpeople and machines to enjoy gigabit data rates with virtually zero(e.g., single digit millisecond) latency. Compared to 4G, 5G supportsmore diverse traffic scenarios. For example, in addition to the varioustypes of data communication between conventional UEs (e.g., phones,smartphones, tablets, PCs, televisions, internet enabled televisions,AR/VR head mounted displays (HMDs), etc.) supported by 4G networks, 5Gnetworks can be employed to support data communication between smartcars in association with driverless car environments, as well as machinetype communications (MTCs). Considering the drastic differentcommunication needs of these different traffic scenarios, the ability todynamically configure waveform parameters based on traffic scenarioswhile retaining the benefits of multi carrier modulation schemes (e.g.,OFDM and related schemes) can provide a significant contribution to thehigh speed/capacity and low latency demands of 5G networks. Withwaveforms that split the bandwidth into several sub-bands, differenttypes of services can be accommodated in different sub-bands with themost suitable waveform and numerology, leading to an improved spectrumutilization for 5G networks.

To meet the demand for data centric applications, features of 5Gnetworks can comprise: increased peak bit rate (e.g., 20 Gbps), largerdata volume per unit area (e.g., high system spectral efficiency - forexample about 3.5 times that of spectral efficiency of long termevolution (LTE) systems), high capacity that allows more deviceconnectivity both concurrently and instantaneously, lower battery/powerconsumption (which reduces energy and consumption costs), betterconnectivity regardless of the geographic region in which a user islocated, a larger numbers of devices, lower infrastructural developmentcosts, and higher reliability of the communications. Thus, 5G networkscan allow for: data rates of several tens of megabits per second shouldbe supported for tens of thousands of users, 1 gigabit per second to beoffered simultaneously to tens of workers on the same office floor, forexample, several hundreds of thousands of simultaneous connections to besupported for massive sensor deployments; improved coverage, enhancedsignaling efficiency; reduced latency compared to LTE.

The 5G access network can utilize higher frequencies (e.g., > 6 GHz) toaid in increasing capacity. Currently, much of the millimeter wave(mmWave) spectrum, the band of spectrum between 30 GHz and 300 GHz isunderutilized. The millimeter waves have shorter wavelengths that rangefrom 10 millimeters to 1 millimeter, and these mmWave signals experiencesevere path loss, penetration loss, and fading. However, the shorterwavelength at mmWave frequencies also allows more antennas to be packedin the same physical dimension, which allows for large-scale spatialmultiplexing and highly directional beamforming.

Performance can be improved if both the transmitter and the receiver areequipped with multiple antennas. Multi-antenna techniques cansignificantly increase the data rates and reliability of a wirelesscommunication system. The use of multiple input multiple output (MIMO)techniques, which was introduced in the 3GPP and has been in use(including with LTE), is a multi-antenna technique that can improve thespectral efficiency of transmissions, thereby significantly boosting theoverall data carrying capacity of wireless systems. The use of MIMOtechniques can improve mmWave communications and has been widelyrecognized as a potentially important component for access networksoperating in higher frequencies. MIMO can be used for achievingdiversity gain, spatial multiplexing gain and beamforming gain. Forthese reasons, MIMO systems are an important part of the 3rd and 4thgeneration wireless systems and are in use in 5G systems.

FIG. 2 illustrates an example general architecture of a systemconfigured to adjust minimum bit rates within a wireless communicationsystem, in accordance with various aspects and embodiments of thesubject disclosure. FIG. 2 includes a network operator 200, a controller210, and a distributed unit (DU) scheduler 220. The controller 210comprises a key performance indicator (KPI) agent 211, a memory 212, acommunication interface 213, and a bit rate adapter 214. The DUscheduler 220 comprises a KPI server 221, a bit rate agent 222, and acommunication interface 223.

In FIG. 2 , the communication interface 213 in the controller 210 can beconfigured to exchange information with RAN nodes, via the DU scheduler220. The communication interface 213 can exchange information with thecommunication interface 223 at the DU scheduler 220. The communicationinterface 213 can furthermore be configured to read input from thenetwork operator 200.

The KPI agent 211 in the controller 210 can be configured to receivenetwork performance related measurements, e.g., performance data 121,126 illustrated in FIG. 1 , in order to evaluate the DU scheduler’s 220current bit rate configurations and the quantity of PRBs allocated tovarious user equipment by the DU scheduler 220.

The bit rate adapter 214 in the controller 210 can be configured to hostbit rate adaptation logic, which can adapt bit rates based on targetKPIs received from the network operator 200 and network conditions. Thememory 212 in the controller 210 can be configured to store the latestbit rate decisions and to create policies which can be evaluated andreused in the future.

Furthermore, the communication interface 223 in the DU scheduler 220 canbe configured to exchange information with the controller 210 and otherRAN nodes, e.g., centralized units (CUs) and radio units (RUs). The bitrate agent 222 in the DU scheduler 220 can be configured to reconfigureminimum bit rates, used by the DU scheduler 220 for each user equipmentbased on real-time bit rate adjustment inputs or previous policiesreceived from the controller 210. The KPI server 221 in the DU scheduler220 can be configured to collect network information for each userequipment and derive corresponding KPIs to be sent to the KPI agent 211.

In example operations according to FIG. 2 , the controller 210 cancontinuously collect user equipment channel conditions and network loadinformation, and can use collected information to estimate optimalminimum bit rates that can be configured for each user equipment. Thecontroller 210 can periodically communicate new minimum bit rates to theDU scheduler 220 to meet target KPIs specified by the network operator200. KPIs can include, e.g., cell throughput targets, spectralefficiency targets, or other performance targets. The controller 210 canalso be configured to satisfy constraints on the minimum bit rate rangesof user equipment. Moreover, the controller 210 can be configured tostore previous minimum bit rate recommendations, for use in evaluatingresultant performance, improving future minimum bit rate targets, andreusing minimum bit rate targets in future decisions under similarnetwork conditions.

In a first example embodiment of the architecture illustrated in FIG. 2, the controller 210 can be implemented as part of a near-real time RIC112, illustrated in FIG. 1 . Such embodiments can aim to decreaseminimum bit rates of user equipment when a target cell throughput is notachieved, and vice versa. This can be done while considering ranges ofallowed bit rates for different user equipment, and target cell spectralefficiency.

In a second example embodiment of the architecture illustrated in FIG. 2, the controller 210 can be configured to learn minimum bit rateconfigurations that lead to improved cell performance for each networkcondition, wherein a network condition can comprise a combination ofsignal strength (e.g., reference signal received power RSRP) conditionsand load (e.g., PRB utilization) conditions. Learned minimum bit rateconfigurations and corresponding network conditions can be stored in aknowledge base which can be iteratively improved based on the achievedbit rate. Such a knowledge base can be used to make future decisionswith a higher probability of recommending an optimal configuration, incomparison to reactive configuration methods.

In a third example embodiment of the architecture illustrated in FIG. 2, the controller 210 can be configured to address intercellinterference. When multiple cells, e.g., a group of cells, are managedby a same controller 210, the controller 210 can configure minimum bitrates of the group of cells such that the intercell interference isdecreased. For example, a first cell may have lower performance thanother cells in the group. The performance of the first cell can beimproved by decreasing a suboptimal minimum bit rate employed by aneighboring cell of the group. The suboptimal minimum bit rate used bythe neighboring cell can be causing excessive interference to the firstcell. Decreasing the suboptimal minimum bit rate can improve performanceof the first cell.

FIG. 3 illustrates an example controller that can implement thecontroller illustrated in FIG. 2 , in accordance with various aspectsand embodiments of the subject disclosure. The example controller 310can implement the controller 210 in some embodiments. The examplecontroller 310 includes various illustrated components and an exampleflow / sequence of the operations. Detect network events 301 can befollowed by collect KPIs 302. Collect KPIs 302 can be followed by detectperformance degradation 303. Detect performance degradation 303 canreceive target KPIs 311 and can be followed by propose new minimum bitrate 304. Propose new minimum bit rate 304 can be followed by storeactions 305. Store actions 305 can be followed by evaluate and improveactions 306. Evaluate and improve actions 306 can be followed by proposenew minimum bit rate 304, so the operations 304, 305 and 306 areillustrated as being performed in a repeating cycle.

In example operations according to FIG. 3 , detect network events 301can be configured to detect events such as new target KPI values from anetwork operator, new users admitted to a cell, or network traffichaving suboptimal minimum bit rate values. In response to a detectednetwork event, detect network events 301 can trigger the controller 310to reconfigure minimum bit rates.

In response to a detected event at 301, the controller 310 can collectKPIs 302. KPIs collected at 302 can include, e.g., user equipment bitrates over a preceding time window of x seconds, an average cellthroughput, and PRB utilization data. In some embodiments, KPIs can becollected from a RAN node based on a request from the controller 310. Inother embodiments, KPIs can be collected from a RAN node periodically.

Detect performance degradation 303 can be configured to compare currentKPIs, collected at 302, with target KPIs 311. When the current KPIs donot meet the target KPIs 311, detect performance degradation 303 cantrigger calculating and proposing new minimum bit rates via 304.

Propose new minimum bit rate 304 can be configured to propose newminimum bit rates for user equipment. In some embodiments, proposed newminimum bit rates can be based on a calculated degree of degradation.Proposed new minimum bit rates can be retrieved from stored values orcan be newly calculated. The new minimum bit rates can be subjected to aset of constraints defined by the network operator, such as lowest andhighest allowed values, which in some circumstances can correspond toapplication specific quality ranges (e.g., video resolutions requiredfor different applications). The new minimum bit rates can be applied toa RAN node for which the new minimum bit rates are determined, asdescribed herein.

Store actions 305 can be configured to store “actions,” e.g., minimumbit rate adjustment values to be applied to user equipment, alongsidenetwork conditions corresponding to such actions. In some embodiments,similar actions can be either grouped or filtered to create a knowledgebase and/or policy to be applied under future detected networkconditions.

Evaluate and improve actions 306 can be configured to observe resultantKPIs from a RAN node to which new minimum bit rates are applied.Subsequent to application of new minimum bit rates, evaluate and improveactions 306 can analyze iterations of KPI data received from the RANnode, and can fine tune minimum bit rate values or the networkconditions at which they shall be applied. For example, if applying newminimum bit rates results in performance that is below a target value,evaluate and improve actions 306 can modify the minimum bit rates to beapplied during a next application of new minimum bit rates to the RANnode.

FIG. 4 illustrates example generation and use of a minimum bit ratepolicy to adjust minimum bit rates, in accordance with various aspectsand embodiments of the subject disclosure. FIG. 4 includes communicationservice provider network(s) 400, network node(s) 430, and example UEs401 and 402. In some embodiments, the communication service providernetwork(s) 400 can implement the communication service providernetwork(s) 110 illustrated in FIG. 1 , the network node(s) 430 canimplement the network node(s) 131, 141 illustrated in FIG. 1 , and theUEs 401 and 402 can implement any of the UEs 132, 133, 134, 142illustrated in FIG. 1 .

The communication service provider network(s) 400 include a non-realtime RIC 410 and a near-real time RIC 420. The non-real time RIC 410includes a policy generator 411, and the non-real time RIC 410 canprovide a modified policy 415 to the near-real time RIC 420. Thenear-real time RIC 420 is illustrated as including the policy 415.

The network node(s) 430 are illustrated as communicating with the UEs401, 402, wherein the communications between network node(s) 430 and UEs401, 402 can use minimum bit rates established for UEs 401, 402. In someembodiments, minimum bit rates can be for uplink communications,downlink communications, or both. The network node(s) 430 can sendperformance data 431 to the communication service provider network(s)400. The performance data 431 can be used by the policy generator 411 togenerate the modified policy 415. The performance data 431 can also beused by the near-real time RIC 420 in connection with determiningminimum bit rate adjustments 432 for the network nodes 430. The minimumbit rate adjustments 432 can be determined by applying the modifiedpolicy 415 to the performance data 431. The minimum bit rate adjustments432 can be sent to the network node(s) 430 for application thereof inconnection with the communications between the network node(s) 430 andthe UEs 401, 402.

FIG. 5 illustrates an example architecture of a system configured togenerate and deploy a policy to adjust minimum bit rates based onnetwork conditions, in accordance with various aspects and embodimentsof the subject disclosure. FIG. 5 includes service management andorchestration 510, near-real time RIC 520 and DU 530. Service managementand orchestration 510 includes a non-real time RIC 512, and the non-realtime RIC 512 includes data collection 513 and policy generation / update514. The near-real time RIC 520 includes performance monitoring 521 andpolicy execution 522. The DU 530 includes scheduler 531.

In FIG. 5 , the policy generation / update 514 can receive target KPIs501. The DU 530 and the service management and orchestration 510 cancommunicate via an O1 interface, whereby the DU 530 can provideperformance data 533 to the service management and orchestration 510.The service management and orchestration 510 and the near-real time RIC520 can communicate via an A1 interface, whereby the service managementand orchestration 510 can provide a minimum bit rate policy 515 to thenear-real time RIC 520. The near-real time RIC 520 and the DU 530 cancommunicate via an E2 interface, whereby the near-real time RIC 520 canprovide minimum bit rate adjustments and other adjustments 523 to the DU530. Furthermore, the DU 530 can provide performance data 532 to thenear-real time RIC 520 via the E2 interface.

In the embodiment illustrated in FIG. 5 , the controller 210 describedin connection with FIG. 2 can be implemented via service management andorchestration 510 and near-real time RIC 520. Embodiments according toFIG. 5 can use performance data 533 to generate a minimum bit ratepolicy 515. The minimum bit rate policy 515 can be provided to thenear-real time RIC 520, and the near-real time RIC 520 can useperformance data 532 and the minimum bit rate policy 515 to determineminimum bit rate and other adjustments 523. The minimum bit rate andother adjustments 523 can be sent to the DU 530 for application to RANcommunications with user equipment.

In some embodiments, the performance data 533 provided to the servicemanagement and orchestration 510 can comprise, inter alia, networkconditions data such as channel data and load data. The channel data caninclude, e.g., reference signal received power (RSRP) data and/orreference signal received quality (RSRQ) data collected from UEs. Theload data can include, e.g., PRB utilization data, including PRBs usedper UE and total PRBs used by a cell. Further example performance data533 can comprise UE throughput data, cell throughput data, RF conditionsdata, and current minimum bit rates applied to UEs.

In some embodiments, the minimum bit rate policy 515 can includerespective network conditions, respective thresholds corresponding tothe respective network conditions, and respective actions correspondingto the respective network conditions and respective thresholds. Theactions can define minimum bit rate adjustments under network conditionsdefined by the network conditions and thresholds. The actions canoptionally further define other adjustments, other than minimum bit rateadjustments, such as adjustments to maximum numbers of PRBs allowed perUE, and adjustments to UE priority ratios. Further description of theminimum bit rate policy 515 is provided below with reference to FIGS. 6,7, and 8 .

In some embodiments, the performance data 532 provided to the near-realtime RIC 520 can comprise, inter alia, data similar or identical to theperformance data 533, described above. The performance data 532 canoptionally comprise a subset of the performance data 533, wherein thesubset enables the near-real time RIC 520 to apply the minimum bit ratepolicy 515.

In some embodiments, the minimum bit rate and other adjustments 523 caninclude minimum bit rate adjustments and/or other adjustments pursuantto actions selected from the minimum bit rate policy 515 by thenear-real time RIC 520. The near-real time RIC 520 can selectappropriate actions from the minimum bit rate policy 515 based on theperformance data 532, and the selected actions can be applied via theminimum bit rate and other adjustments 523. Further example operationsthat can be performed by a system such as illustrated in FIG. 5 aredescribed below with reference to FIG. 6 .

FIG. 6 illustrates an example process to adjust minimum bit rates usinga system such as illustrated in FIG. 5 , in accordance with variousaspects and embodiments of the subject disclosure. FIG. 6 includes thenon-real time RIC 512, the near-real time RIC 520, and the DU 530introduced in FIG. 5 . The non-real time RIC 512 comprises datacollection 513 and policy generation / update 514, as introduced in FIG.5 . The near-real time RIC 520 comprises performance monitoring 521 andpolicy execution 522. The DU comprises scheduler 531.

FIG. 6 illustrates interactions of the illustrated components over time,and a timeline is included at the left side of FIG. 6 . Furthermore,there are two different repeating cycles illustrated in FIG. 6 : therepeating policy update cycle 600, and the repeating bit rate updatecycle 610. One iteration of the illustrated repeating cycles isillustrated, and subsequent iterations of each cycle can be performedsubsequently. Also, multiple iterations of the repeating bit rate updatecycle 610 can optionally be performed during a single correspondingiteration of the repeating policy update cycle 600.

FIG. 6 illustrates data collection 601, whereby the data collectioncomponent 513 can collect performance data 533 from the DU 530. The datacollection component 513 can provide some or all of the collectedperformance data 533 to policy generation / update 514, as data 602.Policy generation / update 514 can generate a new policy or modify apreviously existing policy, resulting in minimum bit rate policy 515.Policy generation / update 514 can provide the minimum bit rate policy515 to the near-real time RIC 520 for further action by policy execution522.

Once in possession of the minimum bit rate policy 515, the near-realtime RIC 520 can apply the minimum bit rate policy 515 as often asdesired, pursuant to the repeating bit rate update cycle 610, until theminimum bit rate policy 515 is replaced by a next minimum bit ratepolicy 515, at which point the near-real time RIC 520 can apply the nextminimum bit rate policy 515. The near-real time RIC 510 can operateusing a control loop which can operate, e.g., in repeating cycles whichcan be repeated every 10 milliseconds (ms) up to 1 second.

In an example bit rate update cycle according to repeating bit rateupdate cycle 610, performance monitoring 521 can be configured toreceive performance data 532 from the DU 530. Performance monitoring 521can filter the performance data 532 and optionally use aspects ofperformance data 532 to look up action(s) in the minimum bit rate policy515. Performance monitoring 521 can provide resulting filtered data andaction requests 611 to policy execution 522. Policy execution 522 can beconfigured to apply the minimum bit rate policy 515 by generating andsending, based on filtered data and action requests 611, minimum bitrate and other adjustments 523 to the DU scheduler 531.

In embodiments according to FIG. 6 , a controller implemented via thenon-real time RIC 512 and the near-real time RIC 520 learns improvedminimum bit rate configurations for each network condition such aschannel (e.g. RSRP) and load (e.g. PRB utilization). Improvedconfigurations can be stored in a knowledge base which is iterativelyimproved based on new collected performance data 533. Such a knowledgebase can be used to make future minimum bit rate decisions with a higherprobability of recommending optimal, or at least improved minimum bitrate configurations, in comparison to reactive configuration approaches.

In some embodiments, an open RAN (ORAN) type architecture can be adoptedto host controller logic. The ORAN architecture can comprise thenon-real time RIC 512 and the near-real time RIC 520, along with otherORAN components.

The non-real time RIC 512 can be configured to maintain a knowledge baseof policy applicable to different network conditions. The policy cancontain network conditions, thresholds, and actions. The networkconditions can be collected via performance data 533 over an O1interface. The network conditions can include, inter alia, PRButilization information and RSRP information. The PRB utilizationinformation can comprise, e.g., a total number of PRBs used to carryuser equipment traffic, divided by a total number of available PRBsavailable to the scheduler 531. The RSRP information can comprise, e.g.,RSRP data reported by UEs as part of cell selection and/or measurementreporting for mobility management.

The thresholds included in a minimum bit rate policy 515 can include,e.g., x1, x2 and U data for each network condition. Thresholds can beinitialized by a network operator based on domain knowledge and can becontinuously improved based on future performance data 533 measurements.

The actions included in a minimum bit rate policy 515 can include, e.g.,improved or optimal values for the minimum bit rates stored in theknowledge base for each network condition (e.g. b1, b2, ...etc.). Forexample, an action can select a low minimum bit rate for user equipmentwith low RSRP, and vice versa. In addition, an action can select a lowermin bitrate when a user equipment’s PRB utilization is high, to avoidnegative impacts on cell throughput.

The non-real time RIC 512 can be configured to evaluate the knowledgebase and adapt the actions corresponding to different network conditionswhen network KPIs are not met. FIG. 8 illustrates example adaptation ofactions under such circumstances. For example, if a minimum bit rate inan action was not achieved for a configured user equipment, then a lowerminimum bit rate value can be stored in an action. That is, a lowerminimum bit rate b_(x) can replace a minimum bit rate b₃ stored in theknowledge base, where a user-achieved bit rate R_(n) can be defined as:

$\text{R}_{n} = \frac{\text{L}_{\text{n}}}{\text{t}_{2} - \text{t}_{1}}$

Where L_(n) is the total number of transmitted bits to user n induration from t₁ to t₂.

Similarly, if a minimum bit rate in an action was only achieved for asubset of the network conditions (e.g. achieved for a recorded RSRP, butonly under lower PRB utilization), then the corresponding networkcondition can be updated, and a modified minimum bit rate policy 515 maybe created.

The non-real time RIC 512 can be configured to send the minimum bit ratepolicy 515 to the near-real time RIC 520 over an A1 interface. The aboveprocedure for the non-real time RIC 512 can be repeated in one or morerepetition cycles, which can optionally occur at a slower pace comparedto the cycles performed by the near-real time RIC 520. In an example,repetition cycles for the non-real time RIC 512 can occur each 0.1-10seconds.

The near-real time RIC 520 can be configured to store the minimum bitrate policy 515 knowledge base received from non-real time RIC 512 overthe A1 interface. Additionally, the near-real time RIC 520 can receiveperformance data 532 from the DU 530 via the E2 interface. Theperformance data 532 can include, e.g., network KPIs such as PRButilization, RSRP and user achieved throughput. The near-real time RIC520 can use the network KPIs to retrieve corresponding actions from theminimum bit rate policy 515 knowledge base, and the near-real time RIC520 can send retrieved actions (i.e. minimum bit rate and otheradjustments 523) to the scheduler 531.

The scheduler 531 can be configured to send performance data 533, e.g.,network KPIs and network conditions, to the non-real time RIC 512 overthe O1 interface. The scheduler 531 can furthermore be configured tosend performance data 532, e.g., network KPIs and network conditions, tothe near-real time RIC 520 over the E2 interface. The scheduler 531 cansend performance data 532 and/or 533 periodically, at certain events(e.g. in response to a user equipment attaching to the cell), or basedon requests from the RICs 512 and 520. In some embodiments, thescheduler 531 can report performance data 532 and/or 533 separately foreach user equipment.

The scheduler 531 can furthermore be configured to receive the minimumbit rate and other adjustments 523 from the near-real time RIC 520, andthe scheduler 531 can be configured to apply the minimum bit rate andother adjustments 523 to each user equipment during resource allocationprocedures.

FIG. 7 is a table representing a portion of an example minimum bit ratepolicy, in accordance with various aspects and embodiments of thesubject disclosure. FIG. 7 includes a policy index column, a conditionscolumn including network conditions, and an actions column includingminimum bit rate actions to apply under the different networkconditions. The network conditions can be associated with thresholds, asshown. Thus, when RSRP < x₁ (where x₁ represents a threshold value), theaction can comprise “min bitrate = b₁”, i.e., set a UE minimum bit rateat the value b₁. FIG. 7 includes various other example networkconditions, thresholds, and actions. The listed examples are notintended to be exhaustive and any network conditions, thresholds, andactions can be included.

FIG. 8 is a table representing example evaluation and update of aminimum bit rate policy, in accordance with various aspects andembodiments of the subject disclosure. FIG. 8 includes a used policycolumn, a monitored network KPI column, an evaluation column, and anactions column. In the first example row, performance data 533 indicatedthat a minimum bit rate b_(x) was achieved by a UE, and b_(x) is greaterthan b₁, where b₁ is the example target minimum bit rate for the UE.Therefore, the evaluation reports a valid policy and actions includekeep current setting. In the example second row, performance data 533indicated that a minimum bit rate b_(x) was achieved by a UE, and b_(x)is less than b₂, where b₂ is the example target minimum bit rate for theUE. Therefore, the evaluation reports a suboptimal policy and actionsinclude updating the policy 515 to set b₂ = b_(x). Various other examplerows provide other examples, and the listed examples are not intended tobe exhaustive and any monitored KPIs, evaluations, and actions can beincluded.

FIG. 9 is a flow diagram representing a set of example operations offirst network equipment, such as the non-real time RIC 512 illustratedin FIG. 5 , in connection with adjusting minimum bit rates based on aminimum bit rate policy, in accordance with various aspects andembodiments of the subject disclosure. The illustrated blocks canrepresent actions performed in a method, functional components of acomputing device, or instructions implemented in a machine-readablestorage medium executable by a processor. While the operations areillustrated in an example sequence, the operations can be eliminated,combined, or re-ordered in some embodiments.

The operations illustrated in FIG. 9 can be performed, for example, bynetwork equipment such as the non-real time RIC 512 illustrated in FIG.5 . The non-real time RIC 512 can generate and deploy a minimum bit ratepolicy 515 by sending the minimum bit rate policy 515 to other networkequipment, such as a near-real time RIC 520. Example operation 902comprises deploying, by network equipment 512 comprising a processor, aminimum bit rate policy 515 for application of the minimum bit ratepolicy 515 by a radio access network node such as DU 530.

The minimum bit rate policy 515 deployed at operation 902 can comprisenetwork conditions, e.g., a group of network conditions, andcorresponding minimum bit rates. Network conditions in the group ofnetwork conditions can comprise channel conditions and load conditions.The channel conditions can comprise reference signal received powerconditions. The load conditions comprise physical resource blockutilization conditions. Furthermore, network conditions in the group ofnetwork conditions can comprise threshold information associated withthe network conditions.

With regard to the minimum bit rates in the minimum bit rate policy 515,at least one first respective minimum bit rate can be correlated with arespective network condition of the group of network conditions. The atleast one first respective minimum bit rate can be for application touser equipment served by the radio access network node 530, in responseto observation of the respective network condition. For example, theobservation of the network condition can be reported via performancedata 532, and the at least one first respective minimum bit rate can besent to the radio access network node 530 in response to performancedata 532.

Operation 904 comprises receiving, by the network equipment 512,performance data 533 related to performance of the radio access networknode 530 during the application of the minimum bit rate policy 515 bythe radio access network node 530. Operation 906 comprises modifying, bythe network equipment 512, the minimum bit rate policy 515 based on theperformance data 533, resulting in a modified minimum bit rate policy515. The initial minimum bit rate policy 515 and the modified minimumbit rate policy 515 are both instances of a minimum bit rate policy 515and so are both referred to by identifier 515 in FIG. 5 .

The modified minimum bit rate policy 515 can comprise modified networkconditions and/or modified minimum bit rates. For example, the modifiedminimum bit rate policy 515 can comprise at least one second respectiveminimum bit rate correlated with the previously described respectivenetwork condition of the group of network conditions. Like the firstrespective minimum bit rate, the at least one second respective minimumbit rate can be for application to the user equipment served by theradio access network node 530 in response to the observation of therespective network condition.

In some cases, modifying the minimum bit rate policy 515 at operation906 can be based on performance data 533 that indicates that a minimumbit rate, e.g., the at least one first respective minimum bit rate, wasnot achieved by the radio access network node 530. Modifying the minimumbit rate policy 515 based on the performance data 533 can compriselowering such a bit rate, e.g., the at least one first respectiveminimum bit rate, resulting in, e.g., the at least one second respectiveminimum bit rate.

In some cases, modifying the minimum bit rate policy 515 at operation906 can comprise modifying network conditions in which a minimum bitrate is applied, resulting in a modified minimum bit rate policy 515that comprises a modified network condition in the group of networkconditions. Another minimum bit rate, e.g., at least one thirdrespective minimum bit rate, can be correlated with the modified networkcondition. Like the first and second respective minimum bit rates, theat least one third respective minimum bit rate can be for application tothe user equipment served by the radio access network node 530 inresponse to an observation of, in this case, the modified networkcondition.

Operation 908 comprises deploying, by the network equipment 512, themodified minimum bit rate policy 515 for application of the modifiedminimum bit rate policy 515 by the radio access network node 530. Forexample, the non-real time RIC 512 can deploy the modified minimum bitrate policy 515 to the real-time RIC 520, for application of themodified minimum bit rate policy 515 by the radio access network node530 under the direction of the real-time RIC 520.

FIG. 10 is a flow diagram representing a set of example operations ofsecond network equipment, such as the near-real time RIC 520 illustratedin FIG. 5 , in connection with adjusting minimum bit rates based on aminimum bit rate policy, in accordance with various aspects andembodiments of the subject disclosure. The illustrated blocks canrepresent actions performed in a method, functional components of acomputing device, or instructions implemented in a machine-readablestorage medium executable by a processor. While the operations areillustrated in an example sequence, the operations can be eliminated,combined, or re-ordered in some embodiments.

The operations illustrated in FIG. 10 can be performed, for example, bynetwork equipment such as the near-real time RIC 520 illustrated in FIG.5 . In general, FIG. 10 illustrates example operations to receive aminimum bit rate policy 515 from by the non-real time RIC 512, and applythe minimum bit rate policy 515 via the DU 530.

Example operation 1002 comprises receiving policy data representative ofa minimum bit rate policy 515 for application via a radio access networknode such as DU 530. The minimum bit rate policy 515 can comprisenetwork conditions, e.g., a group of network conditions, and minimum bitrates correlated with the network conditions. The network conditions inthe group of network conditions can comprise channel conditions and loadconditions. The channel conditions can comprise, inter alia, referencesignal received power conditions. The load conditions comprise, interalia, physical resource block utilization conditions. The networkconditions in the group of network conditions can also comprisethreshold information associated with the network conditions.

The minimum bit rates included in the minimum bit rate policy 515 cancomprise, e.g., at least one respective minimum bit rate correlated witha respective network condition of the group of network conditions. Theat least one respective minimum bit rate can be for application to userequipment served by the radio access network node 530 in response toobservation of the respective network condition.

Example operation 1004 comprises receiving, from the radio accessnetwork node 530, performance data 532 comprising, e.g., the observationof the respective network condition. Example operation 1006 comprisesusing the performance data 532 comprising the observation of therespective network condition to identify, based on the minimum bit ratepolicy 515, the at least one respective minimum bit rate correlated withthe respective network condition. Example operation 1008 comprisessending the at least one respective minimum bit rate to the radio accessnetwork node 530 for application of the at least one respective minimumbit rate by the radio access network node 530.

The operations 1004, 1006, and 1008 can be repeated in a repeating bitrate update cycle 610, at any desired frequency and for any desiredduration. At a future time, optionally after multiple repetitions ofoperations 1004, 1006, and 1008, operation 1010 can occur, e.g.,pursuant to the repeating policy update cycle 600. Operation 1010 cancomprise receiving a modified minimum bit rate policy 515, e.g., fromthe non-real time RIC 512, and replacing the minimum bit rate policy(the initially received minimum bit rate policy 515) with the modifiedminimum bit rate policy 515. Operation 1010 can be followed by returningto the operation 1004 and the repeating bit rate update cycle 610comprising operations 1004, 1006, and 1008.

FIG. 11 is a flow diagram representing a set of example operations ofthird network equipment, such as the radio access network noderepresented by DU 530 in FIG. 5 , in connection with adjusting minimumbit rates based on a minimum bit rate policy, in accordance with variousaspects and embodiments of the subject disclosure. The illustratedblocks can represent actions performed in a method, functionalcomponents of a computing device, or instructions implemented in amachine-readable storage medium executable by a processor. While theoperations are illustrated in an example sequence, the operations can beeliminated, combined, or re-ordered in some embodiments.

The operations illustrated in FIG. 11 can be performed, for example, bynetwork equipment such as the DU 530 illustrated in FIG. 5 . Exampleoperation 1102 comprises sending first performance data, e.g.,performance data 532, wherein the first performance data 532 comprisesnetwork conditions information comprising first network conditionsobserved at the radio access network node 530. Example operation 1104comprises receiving at least one first minimum bit rate, e.g., amongminimum bit rate & other adjustments 523, wherein the at least one firstminimum bit rate (from 523) is based on a minimum bit rate policy 515,and wherein the minimum bit rate policy 515 comprises a correlationbetween the first network conditions and the at least one first minimumbit rate (from 523). Example operation 1106 comprises applying the atleast one first minimum bit rate (from 523) to user equipment served bythe radio access network node 530. Applying the at least one firstminimum bit rate (from 523) to the user equipment can comprise adjustinga minimum bit rate associated with the user equipment according to theat least one first minimum bit rate (from 523).

The operations 1102, 1104, and 1106 can be repeated via operations 1108,1110, and 1112, albeit with different performance data 532 and differentminimum bit rate & other adjustments 523. Furthermore, the repetitioncan continue, as noted in FIG. 11 . Example operation 1108 comprisesobtaining second performance data 532, wherein the second performancedata 532 comprises network conditions information comprising secondnetwork conditions observed at the radio access network node 530 afterapplying the at least one first minimum bit rate (from 523). The secondperformance data 532 can be sent to the near-real time RIC 520. Exampleoperation 1110 comprises receiving at least one second minimum bit rate(e.g., a second transmission of minimum bit rate & other adjustments523), wherein the at least one second minimum bit rate (from a secondinstance of 523) is based on the minimum bit rate policy 515, andwherein the minimum bit rate policy 515 comprises a correlation betweenthe second network conditions 532 and the at least one second minimumbit rate (from a second instance of 523). Example operation 1112comprises applying the at least one second minimum bit rate (from asecond instance of 523) to the user equipment served by the radio accessnetwork node 530. Applying the at least one second minimum bit rate(from a second instance of 523) to the user equipment can compriseadjusting the minimum bit rate associated with the user equipmentaccording to the at least one second minimum bit rate (from a secondinstance of 523).

The repetition of operations 1102, 1104, and 1106 can continue afteroperation 1112, by sending updated performance data 532 and receivingand applying updated minimum bit rate & other adjustments 523.Furthermore, in FIG. 11 , the sending of performance data 532 atoperations 1102 and 1108, and subsequent repetitions thereof, canoptionally be accompanied by sending performance data 533 to thenon-real time RIC 512, so that the non-real time RIC 512 can calculateand provide the modified minimum bit rate policy 515 to the near-realtime RIC 520.

FIG. 12 is a block diagram of an example computer that can be operableto execute processes and methods in accordance with various aspects andembodiments of the subject disclosure. The example computer can beadapted to implement, for example, any of the various network equipmentdescribed herein.

FIG. 12 and the following discussion are intended to provide a brief,general description of a suitable computing environment 1200 in whichthe various embodiments of the embodiment described herein can beimplemented. While the embodiments have been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that theembodiments can be also implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, IoT devices, distributedcomputing systems, as well as personal computers, hand-held computingdevices, microprocessor-based or programmable consumer electronics, andthe like, each of which can be operatively coupled to one or moreassociated devices.

The illustrated embodiments of the embodiments herein can be alsopracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media, machine-readable storage media,and/or communications media, which two terms are used herein differentlyfrom one another as follows. Computer-readable storage media ormachine-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media or machine-readablestorage media can be implemented in connection with any method ortechnology for storage of information such as computer-readable ormachine-readable instructions, program modules, structured data, orunstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), smart card, flashmemory (e.g., card, stick, key drive) or other memory technology,compact disk (CD), compact disk read only memory (CD-ROM), digitalversatile disk (DVD), Blu-ray™ disc (BD) or other optical disk storage,floppy disk storage, hard disk storage, magnetic cassettes, magneticstrip(s), magnetic tape, magnetic disk storage or other magnetic storagedevices, solid state drives or other solid state storage devices, avirtual device that emulates a storage device (e.g., any storage devicelisted herein), or other tangible and/or non-transitory media which canbe used to store desired information. In this regard, the terms“tangible” or “non-transitory” herein as applied to storage, memory, orcomputer-readable media, are to be understood to exclude onlypropagating transitory signals per se as modifiers and do not relinquishrights to all standard storage, memory or computer-readable media thatare not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries, or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 12 , the example environment 1200 forimplementing various embodiments of the aspects described hereinincludes a computer 1202, the computer 1202 including a processing unit1204, a system memory 1206 and a system bus 1208. The system bus 1208couples system components including, but not limited to, the systemmemory 1206 to the processing unit 1204. The processing unit 1204 can beany of various commercially available processors. Dual microprocessorsand other multi-processor architectures can also be employed as theprocessing unit 1204.

The system bus 1208 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1206includes ROM 1210 and RAM 1212. A basic input/output system (BIOS) canbe stored in a non-volatile memory such as ROM, erasable programmableread only memory (EPROM), EEPROM, which BIOS contains the basic routinesthat help to transfer information between elements within the computer1202, such as during startup. The RAM 1212 can also include a high-speedRAM such as static RAM for caching data.

The computer 1202 further includes an internal hard disk drive (HDD)1214 (e.g., EIDE, SATA), one or more external storage devices 1216(e.g., a magnetic floppy disk drive (FDD) 1216, a memory stick or flashdrive reader, a memory card reader, etc.) and an optical disk drive 1220(e.g., which can read or write from a CD-ROM disc, a DVD, a BD, etc.).While the internal HDD 1214 is illustrated as located within thecomputer 1202, the internal HDD 1214 can also be configured for externaluse in a suitable chassis (not shown). Additionally, while not shown inenvironment 1200, a solid-state drive (SSD) could be used in additionto, or in place of, an HDD 1214. The HDD 1214, external storagedevice(s) 1216 and optical disk drive 1220 can be connected to thesystem bus 1208 by an HDD interface 1224, an external storage interface1226 and an optical drive interface 1228, respectively. The interface1224 for external drive implementations can include at least one or bothof Universal Serial Bus (USB) and Institute of Electrical andElectronics Engineers (IEEE) 1394 interface technologies. Other externaldrive connection technologies are within contemplation of theembodiments described herein.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1202, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to respective types of storage devices, it should beappreciated by those skilled in the art that other types of storagemedia which are readable by a computer, whether presently existing ordeveloped in the future, could also be used in the example operatingenvironment, and further, that any such storage media can containcomputer-executable instructions for performing the methods describedherein.

A number of program modules can be stored in the drives and RAM 1212,including an operating system 1230, one or more application programs1232, other program modules 1234 and program data 1236. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1212. The systems and methods described herein can beimplemented utilizing various commercially available operating systemsor combinations of operating systems.

Computer 1202 can optionally comprise emulation technologies. Forexample, a hypervisor (not shown) or other intermediary can emulate ahardware environment for operating system 1230, and the emulatedhardware can optionally be different from the hardware illustrated inFIG. 12 . In such an embodiment, operating system 1230 can comprise onevirtual machine (VM) of multiple VMs hosted at computer 1202.Furthermore, operating system 1230 can provide runtime environments,such as the Java runtime environment or the .NET framework, forapplications 1232. Runtime environments are consistent executionenvironments that allow applications 1232 to run on any operating systemthat includes the runtime environment. Similarly, operating system 1230can support containers, and applications 1232 can be in the form ofcontainers, which are lightweight, standalone, executable packages ofsoftware that include, e.g., code, runtime, system tools, systemlibraries and settings for an application.

Further, computer 1202 can be enabled with a security module, such as atrusted processing module (TPM). For instance, with a TPM, bootcomponents hash next in time boot components, and wait for a match ofresults to secured values, before loading a next boot component. Thisprocess can take place at any layer in the code execution stack ofcomputer 1202, e.g., applied at the application execution level or atthe operating system (OS) kernel level, thereby enabling security at anylevel of code execution.

A user can enter commands and information into the computer 1202 throughone or more wired/wireless input devices, e.g., a keyboard 1238, a touchscreen 1240, and a pointing device, such as a mouse 1242. Other inputdevices (not shown) can include a microphone, an infrared (IR) remotecontrol, a radio frequency (RF) remote control, or other remote control,a joystick, a virtual reality controller and/or virtual reality headset,a game pad, a stylus pen, an image input device, e.g., camera(s), agesture sensor input device, a vision movement sensor input device, anemotion or facial detection device, a biometric input device, e.g.,fingerprint or iris scanner, or the like. These and other input devicesare often connected to the processing unit 1204 through an input deviceinterface 1244 that can be coupled to the system bus 1208, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, a BLUETOOTH®interface, etc.

A monitor 1246 or other type of display device can be also connected tothe system bus 1208 via an interface, such as a video adapter 1248. Inaddition to the monitor 1246, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1202 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1250. The remotecomputer(s) 1250 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all the elements described relative to the computer1202, although, for purposes of brevity, only a memory/storage device1252 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1254 and/orlarger networks, e.g., a wide area network (WAN) 1256. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theinternet.

When used in a LAN networking environment, the computer 1202 can beconnected to the local network 1254 through a wired and/or wirelesscommunication network interface or adapter 1258. The adapter 1258 canfacilitate wired or wireless communication to the LAN 1254, which canalso include a wireless access point (AP) disposed thereon forcommunicating with the adapter 1258 in a wireless mode.

When used in a WAN networking environment, the computer 1202 can includea modem 1260 or can be connected to a communications server on the WAN1256 via other means for establishing communications over the WAN 1256,such as by way of the internet. The modem 1260, which can be internal orexternal and a wired or wireless device, can be connected to the systembus 1208 via the input device interface 1244. In a networkedenvironment, program modules depicted relative to the computer 1202 orportions thereof, can be stored in the remote memory/storage device1252. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

When used in either a LAN or WAN networking environment, the computer1202 can access cloud storage systems or other network-based storagesystems in addition to, or in place of, external storage devices 1216 asdescribed above. Generally, a connection between the computer 1202 and acloud storage system can be established over a LAN 1254 or WAN 1256e.g., by the adapter 1258 or modem 1260, respectively. Upon connectingthe computer 1202 to an associated cloud storage system, the externalstorage interface 1226 can, with the aid of the adapter 1258 and/ormodem 1260, manage storage provided by the cloud storage system as itwould other types of external storage. For instance, the externalstorage interface 1226 can be configured to provide access to cloudstorage sources as if those sources were physically connected to thecomputer 1202.

The computer 1202 can be operable to communicate with any wirelessdevices or entities operatively disposed in wireless communication,e.g., a printer, scanner, desktop and/or portable computer, portabledata assistant, communications satellite, any piece of equipment orlocation associated with a wirelessly detectable tag (e.g., a kiosk,news stand, store shelf, etc.), and telephone. This can include WirelessFidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, thecommunication can be a predefined structure as with a conventionalnetwork or simply an ad hoc communication between at least two devices.

The above description includes non-limiting examples of the variousembodiments. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the disclosed subject matter, and one skilled in the art canrecognize that further combinations and permutations of the variousembodiments are possible. The disclosed subject matter is intended toembrace all such alterations, modifications, and variations that fallwithin the spirit and scope of the appended claims.

With regard to the various functions performed by the above-describedcomponents, devices, circuits, systems, etc., the terms (including areference to a “means”) used to describe such components are intended toalso include, unless otherwise indicated, any structure(s) whichperforms the specified function of the described component (e.g., afunctional equivalent), even if not structurally equivalent to thedisclosed structure. In addition, while a particular feature of thedisclosed subject matter may have been disclosed with respect to onlyone of several implementations, such feature may be combined with one ormore other features of the other implementations as may be desired andadvantageous for any given or particular application.

The terms “exemplary” and/or “demonstrative” as used herein are intendedto mean serving as an example, instance, or illustration. For theavoidance of doubt, the subject matter disclosed herein is not limitedby such examples. In addition, any aspect or design described herein as“exemplary” and/or “demonstrative” is not necessarily to be construed aspreferred or advantageous over other aspects or designs, nor is it meantto preclude equivalent structures and techniques known to one skilled inthe art. Furthermore, to the extent that the terms “includes,” “has,”“contains,” and other similar words are used in either the detaileddescription or the claims, such terms are intended to be inclusive - ina manner similar to the term “comprising” as an open transition word -without precluding any additional or other elements.

The term “or” as used herein is intended to mean an inclusive “or”rather than an exclusive “or.” For example, the phrase “A or B” isintended to include instances of A, B, and both A and B. Additionally,the articles “a” and “an” as used in this application and the appendedclaims should generally be construed to mean “one or more” unless eitherotherwise specified or clear from the context to be directed to asingular form.

The term “set” as employed herein excludes the empty set, i.e., the setwith no elements therein. Thus, a “set” in the subject disclosureincludes one or more elements or entities. Likewise, the term “group” asutilized herein refers to a collection of one or more entities.

The terms “first,” “second,” “third,” and so forth, as used in theclaims, unless otherwise clear by context, is for clarity only anddoesn’t otherwise indicate or imply any order in time. For instance, “afirst determination,” “a second determination,” and “a thirddetermination,” does not indicate or imply that the first determinationis to be made before the second determination, or vice versa, etc.

The description of illustrated embodiments of the subject disclosure asprovided herein, including what is described in the Abstract, is notintended to be exhaustive or to limit the disclosed embodiments to theprecise forms disclosed. While specific embodiments and examples aredescribed herein for illustrative purposes, various modifications arepossible that are considered within the scope of such embodiments andexamples, as one skilled in the art can recognize. In this regard, whilethe subject matter has been described herein in connection with variousembodiments and corresponding drawings, where applicable, it is to beunderstood that other similar embodiments can be used or modificationsand additions can be made to the described embodiments for performingthe same, similar, alternative, or substitute function of the disclosedsubject matter without deviating therefrom. Therefore, the disclosedsubject matter should not be limited to any single embodiment describedherein, but rather should be construed in breadth and scope inaccordance with the appended claims below.

What is claimed is:
 1. A method, comprising: deploying, by network equipment comprising a processor, a minimum bit rate policy for application of the minimum bit rate policy by a radio access network node, wherein the minimum bit rate policy comprises: a group of network conditions; and at least one first respective minimum bit rate correlated with a respective network condition of the group of network conditions, wherein the at least one first respective minimum bit rate is for application to user equipment served by the radio access network node in response to observation of the respective network condition; receiving, by the network equipment, performance data related to performance of the radio access network node during the application of the minimum bit rate policy by the radio access network node; and modifying, by the network equipment, the minimum bit rate policy based on the performance data, resulting in a modified minimum bit rate policy, wherein the modified minimum bit rate policy comprises at least one second respective minimum bit rate correlated with the respective network condition of the group of network conditions, and wherein the at least one second respective minimum bit rate is for application to the user equipment served by the radio access network node in response to the observation of the respective network condition.
 2. The method of claim 1, further comprising deploying, by the network equipment, the modified minimum bit rate policy for application of the modified minimum bit rate policy by the radio access network node.
 3. The method of claim 1, wherein the network conditions in the group of network conditions comprise channel conditions and load conditions.
 4. The method of claim 3, wherein the channel conditions comprise reference signal received power conditions.
 5. The method of claim 3, wherein the load conditions comprise physical resource block utilization conditions.
 6. The method of claim 1, wherein the network conditions in the group of network conditions comprise threshold information associated with the network conditions.
 7. The method of claim 1, wherein the performance data indicates that the at least one first respective minimum bit rate was not achieved by the radio access network node, and wherein modifying the minimum bit rate policy based on the performance data comprises lowering the at least one first respective minimum bit rate, resulting in the at least one second respective minimum bit rate.
 8. The method of claim 1, wherein the modified minimum bit rate policy further comprises a modified network condition in the group of network conditions, and at least one third respective minimum bit rate correlated with the modified network condition, and wherein the at least one third respective minimum bit rate is for application to the user equipment served by the radio access network node in response to an observation of the modified network condition.
 9. The method of claim 1, wherein the network equipment comprises a non-real time radio access network intelligent controller, and wherein the network equipment deploys the minimum bit rate policy by sending the minimum bit rate policy to a radio access network intelligent controller.
 10. Network equipment, comprising: a processor; and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising: receiving policy data representative of a minimum bit rate policy for application via a radio access network node, wherein the minimum bit rate policy comprises: a group of network conditions; and at least one respective minimum bit rate correlated with a respective network condition of the group of network conditions, wherein the at least one respective minimum bit rate is for application to user equipment served by the radio access network node in response to observation of the respective network condition; receiving, from the radio access network node, performance data comprising the observation of the respective network condition; using the performance data comprising the observation of the respective network condition to identify, based on the minimum bit rate policy, the at least one respective minimum bit rate correlated with the respective network condition; and sending the at least one respective minimum bit rate to the radio access network node for application of the at least one respective minimum bit rate by the radio access network node.
 11. The network equipment of claim 10, wherein the network conditions in the group of network conditions comprise channel conditions and load conditions.
 12. The network equipment of claim 11, wherein the channel conditions comprise reference signal received power conditions.
 13. The network equipment of claim 11, wherein the load conditions comprise physical resource block utilization conditions.
 14. The network equipment of claim 10, wherein the network conditions in the group of network conditions comprise threshold information associated with the network conditions.
 15. The network equipment of claim 10, wherein the network equipment comprises a near-real time radio access network intelligent controller, and wherein the network equipment receives the minimum bit rate policy from a radio access network intelligent controller.
 16. The network equipment of claim 10, wherein the operations further comprise receiving a modified minimum bit rate policy and replacing the minimum bit rate policy with the modified minimum bit rate policy.
 17. A non-transitory machine-readable medium, comprising executable instructions that, when executed by a processor of a radio access network node, facilitate performance of operations, comprising: sending first performance data, wherein the first performance data comprises network conditions information comprising first network conditions observed at the radio access network node; receiving at least one first minimum bit rate, wherein the at least one first minimum bit rate is based on a minimum bit rate policy, and wherein the minimum bit rate policy comprises a correlation between the first network conditions and the at least one first minimum bit rate; and applying the at least one first minimum bit rate to user equipment served by the radio access network node, wherein applying the at least one first minimum bit rate to the user equipment comprises adjusting a minimum bit rate associated with the user equipment according to the at least one first minimum bit rate.
 18. The non-transitory machine-readable medium of claim 17, wherein the operations further comprise obtaining second performance data, and wherein the second performance data comprises network conditions information comprising second network conditions observed at the radio access network node after applying the at least one first minimum bit rate.
 19. The non-transitory machine-readable medium of claim 18, wherein the operations further comprise receiving at least one second minimum bit rate, wherein the at least one second minimum bit rate is based on the minimum bit rate policy, and wherein the minimum bit rate policy comprises a correlation between the second network conditions and the at least one second minimum bit rate.
 20. The non-transitory machine-readable medium of claim 19, wherein the operations further comprise applying the at least one second minimum bit rate to the user equipment served by the radio access network node, and wherein applying the at least one second minimum bit rate to the user equipment comprises adjusting the minimum bit rate associated with the user equipment according to the at least one second minimum bit rate. 